home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93b.txt
/
000125_icon-group-sender _Mon May 31 11:43:54 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-06-16
|
1KB
Received: from owl.CS.Arizona.EDU by cheltenham.CS.Arizona.EDU; Mon, 31 May 1993 12:04:15 MST
Received: by owl.cs.arizona.edu; Mon, 31 May 1993 12:04:14 MST
Date: Mon, 31 May 1993 11:43:54 MST
From: "Clint Jeffery" <cjeffery>
Message-Id: <199305311843.AA02129@chuckwalla.cs.arizona.edu>
To: icon-group@cs.arizona.edu
Subject: Re: Icon on a mixed-architecture network
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
ron@mlfarm.com (Ronald Florence) writes:
>I'm wondering what is the best way to install Icon on a network with
>both Sun4 and Sun3 machines.
...
>will the same executable run on either system?
The easiest way to find out is probably to try it (and let us know!).
In addition to the executable header and byte-order issues which you've
already thought of, there are at least two more potential problems that
come to mind:
1) word alignment: I believe Sparcs are longword aligned.
2) C structure layout: icode includes various data in C
structure format, and the icont and iconx had better
agree on what they look like in memory.